Messaging systems and methods

ABSTRACT

A messaging system may include an account module that maintains user accounts associated with user identifying data that include a first password required to access the user account. The messaging system may receive message data including a message and identification of one or more of the user accounts the message is to be shared. Upon request, the messaging system may issue a second password to one of the user accounts. When the second password is used to access the user account, the user account may revert to an original state wherein all personalized information, including payment information, associated with the user account is deleted and unrecoverable.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/741,462, filed Jan. 13, 2020, now U.S. patent Ser. No. 11/017,111,which is a continuation of U.S. patent application Ser. No. 15/942,981,filed Apr. 2, 2018, now U.S. Pat. No. 10,534,926, which is acontinuation of U.S. patent application Ser. No. 14/875,109, filed Oct.5, 2015, now U.S. Pat. No. 9,934,396, which is a divisional of U.S.patent application Ser. No. 14/279,444, filed May 16, 2014, now U.S.Pat. No. 9,361,476. U.S. patent application Ser. No. 16/741,462, U.S.patent application Ser. No. 15/942,981, U.S. patent application Ser. No.14/875,109, and U.S. patent application Ser. No. 14/279,444 are herebyincorporated herein by reference.

INVENTIVE FIELD

The present application relates to electronic communications, and morespecifically to single instance electronic messaging systems and methodsof user notification of messages.

BACKGROUND

Increasing use of electronic communication devices to effectuatemessaging in electronic environments has vastly improved the speed andease in which communications may be exchanged. With these improvements,however, a number of drawbacks arise from such communications. Onedrawback is a concern over privacy in both the short term and long term.For example, multiple or subsequent users of electronic communicationdevices may not be intended to view communications or receivenotification that communication has previously or is taking place.Inability to modify such messages in collaborative environments is alsoa common drawback. In view of above, what is needed are messagingsystems and methods that more adequately address privacy concerns andincrease ability to collaborate.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the described embodiments are set forth withparticularity in the appended claims. The described embodiments,however, both as to organization and manner of operation, may be bestunderstood by reference to the following description, taken inconjunction with the accompanying drawings in which:

FIG. 1 is a schematic of a messaging system according to variousembodiments described herein;

FIG. 2 is a schematic of a messaging system according to variousembodiments described herein;

FIG. 3 is a schematic of a messaging system according to variousembodiments described herein;

FIG. 4 is a schematic of a messaging system according to variousembodiments described herein;

FIG. 5 is a schematic of a messaging system according to variousembodiments described herein;

FIG. 6 is a schematic of a messaging system according to variousembodiments described herein;

FIG. 7 is a schematic of a messaging application comprising a messagingfunction and a game function according to various embodiments describedherein;

FIGS. 8A-8C schematically illustrate portions of a password resetfunction 863 according to various embodiments described herein;

FIG. 9 is a navigation diagram of a website interface for messagingprogram according to various embodiments described herein;

FIG. 10 illustrates features of a message details page according tovarious embodiments described herein;

FIG. 11 illustrates features of a contacts page according to variousembodiments described herein;

FIG. 12 illustrates features of an account information or settings pageaccording to various embodiments described herein; and

FIG. 13 is a navigation diagram of a messaging function or portion 987of a messaging application according to various embodiments describedherein.

SUMMARY

In one aspect, a messaging system for providing messaging servicebetween or among user accounts comprises a message database server. Themessage database server comprises an account module configured tomaintain a plurality of user accounts, an upload module configured toreceive message data from a user communication device associated with auser account. The message data may comprise a message and a share listthat authorizes one or more identified user accounts in which themessage is to be shared. A single instance storage module may beconfigured to store the message as a single instance. A share module maybe configured to share the message with the one or more user accountsidentified in the share list and delete the message at a predeterminedtime as specified in the share list.

In a further aspect, the share list authorizes one or more usermodification privileges to be provided to at least one of the one ormore identified user accounts. The authorized one or more usermodifications may include modification of at least the message or theshare list. The user modification privileges may include one or more ofediting privileges, deletion privileges, modification of shareprivileges with respect to one or more identified user accounts, andidentification of additional user accounts in which the message is to beshared. The share list may provide a directive with respect to a time,time period, or an event that is to trigger deletion of the message datafrom the system. The share module may be configured to delete themessage from the single instance storage module in accordance with thedirective defined in the share list.

In a further aspect, the plurality of user accounts maintained in theaccount module may comprise user identifying data. The share module maycomprise a notification module configured to generate a notification ofthe message to one or more user accounts in which the message isauthorized to be shared. The user identifying data may be used by themessage database server to identify one or more user communicationdevices to which the notification module is to transmit the generatednotification. The plurality of user accounts maintained in the accountmodule may comprise user notification preferences. The notificationmodule may be configured to transmit the notification to the one or moreuser communication devices according to the notification preferences.The share module may comprise a retention module configured to clean themessage database server of the notification and the messaging data,including the share list, when the message is deleted. The identifyingdata may comprise a password and access to the user account may requireentering the password. The system may further comprise a password resetfunction configured to provide a temporary password to the user accountupon request. The functionality of the temporary password and a previouspassword remain until one of the passwords is used. If the previouspassword is used first, the temporary password is terminated. If thetemporary password is used first, the user account will revert back toan original state wherein all personal settings, message data authorizedto share, and contacts are deleted and unrecoverable. The identifyingdata may comprise a username or userID. Modification of the username oruserID may modify the username or userID associated with the user in alladdress books and block lists that include the username or userID, forexample, a reference to pervious username or userID.

In another aspect, a messaging application configured to run on a usercommunication device to interface with a message database servercomprises a messaging function and a secondary function integrated withthe messaging function and configured to obscure the messaging function,wherein the messaging application is configured to be associated with auser account of the message database server and to present anotification of a message stored in the message database server in whichthe associated user account is authorized to access.

In a further aspect the notification may be presented as a crypticnotification disguised as an in-operation event within the operation ofthe secondary function. The messaging application may be configured topresent identifying data to the message database server to associate themessaging application with the associated user account. The messagingapplication may be configured to receive or obtain notifications of newmessages stored as single instances in the message database server whichthe associated user account is authorized to access. The messagingfunction may be configured to allow message data comprising messages tobe prepared, uploaded, accessed, and modified from the usercommunication device without the message data needing to be stored onthe user communication device. The messaging application may comprise aquery module configured to query the message database server fornotifications identifying the associated user account of availablemessages. The messaging application may be configured translate thenotification into the in-operation event for presentation within theoperation of the secondary function.

In a further aspect, the secondary function comprises a game functionincluding a mobile game application configured to be run or simulated onthe user communication device. The messaging application may comprise alogin prompt configured to appear within the game function. The loginprompt may be configured to receive user identifying data toauthenticate the associated user account and thereafter provide accessto the authenticated user account and the messages identifying theauthenticated user account. The messaging application may comprise auser interface including one or more interactive menus that may bemanipulated to reveal the login prompt on the user communication device.The messaging application may be configured to block access to themessaging function and return to the game function when correctidentifying information is not received in the login prompt. Themessaging application may comprise a stand-by mode in which themessaging function is obscured and the game function is fullyoperational. When the messaging application receives notification of amessage, the messaging application may translate the notification to thein-game notification. The in-game notification may comprise one of asound and vibration that is obscured as a notification that a game eventis available or happened. The in-game notification may be customizableto provide details with respect the message to indicate at least one ofa user account that uploaded the message, time until deletion of themessage, and at least one other user account authorized to access themessage. The message database server may be configured to store messagesas single instances. Access to a message stored as single instances maybe specified in a share list that identifies two or more user accountsauthorized to view, edit, and delete the message.

In still a further aspect, a messaging system may include a notificationmodule that generates a cryptic notification of one or more messagesavailable to a first user account from one or more second user accounts.The system may receive user notification preference settings for thefirst user account via a user interface of an electronic usercommunication device that predefines the cryptic notification to begenerated by the notification module for display by the usercommunication device when a message is available. The crypticnotification may be predefined to be cloaked as an event or operationunrelated to notification of an available message. The system maygenerate the predefined cryptic notification for display by the usercommunication device when a message is available to the first useraccount.

DETAILED DESCRIPTION

According to various embodiments described herein, a messaging systemand method may be employed to provide drop dead messaging overelectronic communication routes. Drop dead messaging generally includesability of messaging users to communicate via messages in aninconspicuous manner, which, in some instances, includes communicatingor providing messages in an environment wherein the messages or evenmere notification of messages may be perceivable by others. Forinstance, a user providing a message may want to notify intendedrecipients or users that the message is available and where the messageis located. Since it is contemplated that others may perceive thenotification, the messaging systems and methods may include featuresconfigured to obscure the true purpose of the notification or even thatthe notification is in fact a notification. The substance of themessages may be social, business, educational, literary, mathematical,collaborative, peer review, technical, or any other message formsuitable to be sent between and among users of the messaging system.

FIG. 1 is a generalized schematic of the basic organization of amessaging system 100 according to various embodiments. The messagingsystem 100 comprises a message database server 110. The message databaseserver 110 may include various components and modules to perform themessaging operations disclosed herein. It is to be appreciated that thecomponents or modules may include or use, including share, resources,hardware, processor, services, networking and communication interfacesused to access the Internet, intranets or extranets via wire, Wi-Fi, orWireless Wide Area Networkers, memory, data storage mediums, or variousresources or peripherals and may or may not be present in a singlephysical location. In one embodiment, the message database serverincludes a data storage medium 111 (e.g., hard disk, solid statestorage, etc.) and a logic control unit 112 that may include a datastorage controller configured to store single instance messages as wellas user account data in the data storage medium 111. The logic controlunit 112, such as an electronic data or computer processor, e.g.,central processing unit, may be configured to receive, transmit,communicate, process, modify, maintain, provide or prevent access,distribute, delete, etc. messaging system data according to a messagingprogram. The messaging program may include a set of instructions whichmay include software, protocols, and the like, that may be executed toperform the operations of the message database server. As described inmore detail below, the data storage medium 111 may further be configuredto store one or more user messaging accounts and associated data.

The messaging system 100 also comprises a communication interface 113.The communication interface 113 may be configured to communicate withuser communication devices 114 via electronic communication (e.g.,wired, wireless, telecommunication, internet, intranet, extranet viaWi-Fi or Wireless Wide Area Networks etc.). User communication devices114 may include electronic communication devices such phones, PDAs,mobile devices, mobile or cellular phones, smartphones, personalcommunication devices, electronic computing devices having communicationcapabilities such as computers, desktops, laptops, tablets, mainframes,etc. In various embodiments, communication may include the messagingprogram interfacing with a user messaging application e.g., via avirtual or distributed network, and may include a gateway, switch,router, modem, network adaptor, telecommunications transceiver,software, webpage, etc. configured to interface with users devices 114and perform transmission, reception, and other communication functionsof the system 100. For instance, messaging and communication of databetween the message database server 110 and the user communicationdevice 114 may be provided by the communication interface 113 accordingto protocols defined by the messaging program or user messagingapplication, which may include website or mobile applications stored on,accessible by, actually or virtually executed on, or otherwiseconfigured to provide a user interface capabilities with the messagedatabase server or messaging program.

In various embodiments, the messaging system 110, communicationinterface 113, messaging program or application, or user communicationdevices 114 are configured to transmit data using secure communicationroutes and protocols. In one embodiment, the messaging application maybe used to associate the communication device 114 with a user account,e.g., by presenting identifying data to the messaging server database.In some embodiments, messaging and communication of data may betransmitted using layered security or other adequate security measuresdesigned to encrypt or otherwise secure the transmitted data fromunwanted access, eavesdroppers, or tampering. In one embodiment, forexample, messaging or communication may be transmitted using transportlayer or secure sockets security protocols.

In some embodiments, a user may establish a user account with themessage database server 110. The user account and user data associatedwith the account is typically stored and maintained by the messagedatabase server 110 in the data storage medium 111. In some embodiments,however, a portion of user data associated with the account may be atleast partially stored or maintained in a storage medium associated withthe user communication device 114, which may include a user messagingapplication configured to run or interface with the message databaseserver 110 at the communication interface 113 to execute a user sideportion of the messaging program. Thus, in some embodiments, users maycommunicate with the message database server 110 using usercommunication devices 114 and thereby access their user account.

In one embodiment, the messaging system 100 includes a messagingcommunity comprising a plurality of user accounts. User accounts mayinclude or be associated with user account data. The user account datamay generally include settings such as preferences, notifications, useraddresses or names, and identifying data. At least a portion of useraccount data is provided by the user. In one embodiment, preferences maybe with respect to routes or manner of receiving notifications. Forexample, a user may provide an address, e.g., a phone number, emailaddress, web address, social networking address, or electronic messagingaddress, in which the user would like to receive notifications. Theaddress may be specific to a user communication device 114, such as adevice identification address, or may be a more general address in whichthe notification may be accessed from multiple user communicationdevices 114.

In general, user identifying data may include a userID, username,password, device or application identifications, or other identifyingdata. Each user account may be associated with a userID foridentification within the messaging community. In some embodiments,users accounts may be identified via the user communication device 114such that the system 100 may associate the user account with aparticular communication device 114 assigned to or holding the useraccount without additional identifying information associated with theuser being presented. For example, the user account may be associatedwith identification associated with the user communication device 114 ora messaging application installed on the user communication device 114.In some embodiments, the user account may be associated with a usernameor password to verify the user or access to the user account. Forexample, the system 100, message database server 110, user account, ormessaging application may require entry of a username or password tologon, receive notifications, perform messaging actions, or access theuser account.

As stated above, user accounts may be associated with a username,userID, or both. The userID may be used by the messaging system 100community of user accounts to identify the user, e.g., the holder of theaccount, or the user account for communicating messages. The userID mayinclude a public username that may be used by other account holders toidentify the user. The username may be the same as the userID or may bea private user account identifier used by the system 100 or databaseserver 110 for verification of identity or logon. Thus, the user maydisassociate its community identifier from the system 100 identifier.For example, if one of the username or userID is compromised, e.g.,someone else views their username, the user or user account is notnecessarily “outed” with respect to the other because the two have beendisassociated. In some embodiments, the username may be associated withthe userID and thus may be the same. According to one embodiment, theuser may associate and disassociate the username and userID associatedwith their user account when desired, possibly for a fee. Thus, ifeither the userID or username is compromised, the user may change one ofthe userID or the username. The user may be prompted to enter theirusername and password to verify access to log onto the message databaseserver 110, e.g., their user account, or a messaging application thatmay be run from the user communication device 114 and interface with themessage database server 110. Notably, whether associated ordisassociated, the userID and username will be generally associated withthe user account by the system 100. In certain embodiments,notifications may be provided to the user communication device 114 butaccess to the message or message functions may require additionalidentifying information, e.g., username or password.

A user may obtain an account by accessing a webpage and creating anaccount or creating an account through a mobile application. The accountmay be tied to the user communication device 114 or application or maybe accessed via other user communication devices through the webpage ormobile application. In one embodiment, accounts must be set up throughthe webpage and may not be set up through the mobile application. Inanother embodiment, accounts may only be set up through the mobileapplication.

User account data may also include a user address book. The user addressbook may be used to obtain, hold, search, or contain one or more useraddresses or userID associated with other user accounts. Typically, theaddress book contains addresses or userIDs of users in which the usercommunicates or intends to communicate. In some instances, the addressbook or more generally the user data includes a block list. The user mayuse the block list to identify other users to block messages ornotifications of such messages or the ability of a blocked user fromlisting the user on a share list associated with the message.

It is to be appreciated that unless stated otherwise the elementsdescribed herein may be applied in combinations other than thoseexemplified in the figures. Furthermore, unless stated otherwise thedisclosed systems, methods, and devices for use in the systems ormethods may include fewer or additional elements than illustrated andunless stated otherwise particular elements and combinations of elementsmay not be required in all embodiments.

FIG. 2 schematically illustrates various components and operations of amessaging system 200 and operations thereof according variousembodiments. The messaging system 200 includes a database server 210,which may be similar to database server 110, configured to run amessaging program. Those skilled in the art will appreciate that themessaging system 200 may be implemented in various configurations andtherefore such configurations are to be considered included herein. Thedatabase server 210 comprises a communication interface 213, which maybe similar to communication interface 113, configured to interfacecommunications between the database server 210 and user communicationdevices 214. The database server 210 further comprises an account module215 configured to maintain user accounts 216 and data associated withthe user accounts 216, such as messages 217, preferences 218, sharelists 219, or identifying information 220, which may be stored in a datastorage medium such as data storage medium 112. The account module 215includes a single instances storage module 225 configured to storemessages 217 as single instances and interface with the communicationinterface 213 to handle single instance reception, storage,modification, presentation, and deletion of messages 217. In someembodiments, the account module 215 generates message referencesreferencing single instance messages 217 stored in the single instancestorage module in user accounts 216 identified in a share list 218associated with the referenced message. The user accounts 216 may beaccessed by associated, identified, or verified users of the account 216via user communication devices 214, such as electronic communicationdevices through communication interface 213. As described in more detailbelow, user communication devices 214 may be operatively associated,e.g., programed to run, a user messaging application configured tointerface with the database server 210 at the communication interface213. The messing application may be associated with a user account 216via a login function. The user communication device 214 may also beassociated with the user account 216 or the messaging application foridentification of the user and user account 216. User identifying datamay be held in one or more of the user account 216, in the messagingapplication, and the user communication device 214 to identify the userand associate the application, communication device 216, and useraccount 216. In one embodiment, the message server database 210 includesthe messaging program operable to interface with user communicationdevices 214 at a webpage. Users may access the webpage and provide useridentifying data, such as a username or password to log onto their useraccount 216 and access messages 217.

The system 200 further includes an upload module 225 which may beassociated with the communication interface 213 configured to provideuser upload functionalities with respect to the database server 210 andassociated accounts 216. For examples, a user may use a communicationdevice 214 to interface with the communication interface 213 of thedatabase server 210 and upload data 226, e.g., messages 217, preferences218, lists 219, identification data 220, and other information to beassociated with their user account 216 via the upload module 225. Theaccount module 215 and single instance storage module 221 may beconfigured to cooperate or operatively interface with the upload module225 to receive and store messages 217 as single instances.

The system 200 may further include a share module 230 configured toprovide share functionalities. For example, a user may use acommunication devices 214 to upload a share list 219 associated with oneor more messages 217 that are associated with the user's account 216maintained by the account module 215 which includes the one or moremessages 217 stored as a single instance by the single instance storagemodule 221. Share lists 219 may specify one or more other users that areauthorized to view or take action with respect to an uploaded message217. The share module 230 uses the share list 219 to provide access orsharing, e.g., single instance access, to users, user communicationdevices 214, or user accounts 216 identified in the share list 219. Atleast initially, only users or associated accounts 216 or devices 214specified in the share list 219 are authorized to view the message 217.The message 217 may exists in the single instance storage module 221 ofthe system 200, e.g., a data storage medium 112 associated with themessage database server 110, 210, as only a single instance andtypically may be deleted by the author or one of the specified users inthe share list 219, when such authority has been provided in the sharelist 219. The share module 230 may be configured to retain share lists219 and generate message references referencing single instance messages217 stored in the single instance storage module in user accounts 216identified in a share list 219. Thus, the share module 230 may interfacewith user communication devices 214 to access and display user accountsthrough the account module 215. The share module 230 may use referencesto messages 217 stored in the single instance storage module 221 in useraccounts to identify messages 217 to be shared with the user. In oneembodiment, the share module 230 receives the share list 219 andgenerates a message ID for the message 217 and links the message ID withthe identified user accounts 216. In another embodiment, the sharemodule 230 retains references correlating user accounts 216 withmessages 217 in which the account 216 has been identified in a sharelist 219. In another embodiment, the share lists 219 are retained by theshare module 230 such that when the share module interfaces with a usercommunication device 214, the share module 230 may present a list ofmessages 217 available for the user. The share module 230 may thenaccess the message 217 from the single instance storage module 221 andpresent it to the user. The share module 230 may also generatereferences in the user accounts 216 identifying certain messages 217when the share module 230 maintains the share lists 219.

FIG. 3 schematically illustrates various components and operations of amessaging system 300 according to various embodiments. The messagingsystem 300 comprises a message database server 310 configured formessaging functions comprising uploading and sharing messages. Themessaging system 300 may include elements similar to those describedabove with respect to messaging systems 100 and 200 or the other systemsherein disclosed. For brevity, those elements having already beendescribed with respect to preceding examples may not be again describedor described in similar detail. Similar elements have been similarlyidentified in the figures. The message database server 310 may comprisea logic control module configured to execute the messaging program,which may at least partially embodied in instructions residing inmemory, e.g., software, which may be employed to execute the operationsof the message database server 310. Thus, the message database server310 may comprise combinations of software, virtual or distributednetworks, hardware such as memory, electronic storage mediums, logic andstorage control units, electronic processors such as processing unitsand the like. The logic control module may therefore include or beassociated with various message database server 300 hardware andsoftware which may be employed to execute the operations of the messagedatabase server 310 according to the messaging program. The messagingsystem 300 and database server 310 may be as described above andgenerally comprise various components and modules configured to receiveand control storage, modification, and access to a messaging as well asmanage user accounts 316 or user account data.

The message database server 310 comprises a communication interface 313having an account module 315 configured to maintain user accounts 316,three of which are shown 316 a, 316 b, 316 c, and including a singleinstance storage module 321 configured to store uploaded messages 317 a,317 b, a share module 330 configured to receive uploaded share lists 319a, 319 b and perform specified share operations as specified in theshare list 319, and an upload module 325 configured receive and uploaddata 317 a, 317 b, 319 a, 319 b,

Still referring to FIG. 3 , a first user communication device 314 a isshown uploading a first message 317 a and a second message 317 b to theupload module 325. The first user communication device 314 a is alsoshown uploading a first share list 319 a identifying first, second, andthird user accounts 316 a, 316 b, 316 c in which the first message 317 ais to be shared. The user communication device 314 a is also shownuploading a second share list 319 b identifying user accounts 316 a, 316b in which the second message 317 b is to be shared. Thus the usercommunication device 314 a may upload a first share list 319 aidentifying user first, second, and third user accounts 316 a, 316 b,316 c authorized to share/access the first message 317 a and a secondshare list 319 b identifying first and second user accounts 316 a, 316 bauthorized to share/access the second message 317 b. The first andsecond share lists 319 a, 319 b may specificity the level or sharing orprivilege with respect to message actions authorized to be taken by eachuser account 316 a, 316 b, 316 c, e.g., edit, delete, additional orfewer user accounts to share, etc. In one embodiment, the singleinstance storage module 321 may be configured to receive the first andsecond messages 317 a, 317 b from the upload module and store the firstand second messages 317 a, 317 b as single instances.

In system 300, the share module 330 is configured to provide aninterface with the first, second, and third user accounts 316 a, 316 b,316 c and generate message references 317 a′, 317 b′ in the first,second, and third user accounts 316 a, 316 b, 316 c in which the useraccount 316 a, 316 b, 316 c, e.g., the associated userID, has beenidentified in a share list 319 a, 319 b associated with a message 317 a,317 b maintained as a single instance in the single instance storagemodule 321. The share module 330 may be configured to receive the firstand second share lists 319 a, 319 b from the upload module 325 andassociate the first and second share lists 319 a, 319 b with therespective first and second messages 317 a, 317 b stored as singleinstances in the single instance storage module 321. In variousembodiments, the share module 330 is configured to receive the first andsecond share lists 319 a, 319 b and generate or receive a message IDfrom the single instance storage module 321 for identifying the firstand second messages 317 a, 317 b. For example, the share module 330 mayobtain or generate a message ID that identifies the first and secondmessage 317 a, 317 b such that the first and second message 317 a, 317 bmay be accessed by the share module 330. The share module 330 mayassociate the message ID with the one or more userIDs or user accounts316 a, 316 b, 316 c identified in the share list 319 a, 319 b. Forexample, the share module 330 may associate the message ID with the onemore userIDs or accounts 316 a, 316 b, 316 c together or individually.The share module 330 may also be configured to provide a messagereference 317 a′, 317 b′ in the user accounts 316 a, 316 b, 316 cidentified by the share list 319 a, 319 b. In some embodiments, themessage references 317 a′, 317 b′, 317 c′ may include privilege levels.The share module 330 may also update the references 317 a′, 317 b′, 317c′, e.g., when privilege levels have changed or when the message 317 a,317 b has been edited.

In one embodiment, the user accounts 316 a, 316 b, 316 c may include amessage view including a list of messages that the user account 316 a,316 b, 316 c or userID associated with the user account 316 a, 316 b,316 c has been authorized to access. In various embodiments, the sharemodule 330 may provide an interface to user account data including suchmessaged data. The message view may include a list of relevant datesassociated with the messages 317 a, 317 b. For example, the useraccounts 316 a, 316 b, 316 c may include a list the dates that messages317 a, 317 b have been edited or are slated for deletion. In oneembodiment, the user accounts 316 a, 316 b, 316 c may list other dataassociated with messages 317 a, 317 b such as other users or useraccounts 316 a, 316 b, 316 c authorized to access the message 317 a, 317b. The list may additionally or alternatively include privilege levelsauthorized for the user or other user accounts 316 a, 316 b, 316 c withrespect to the particular message 317 a, 317 b, 317 c, author of themessage 317 a, 317 b, dates that actions have been taken, date theparticular message 317 a, 317 b, 317 c is to be deleted, particularactions taken by the other authorized user accounts 316 a, 316 b, 316 c.

In one embodiment, a message 317 a, 317 b and associated share list 319a, 319 b are maintained by the single instance storage module 321, as insystem 200, and the share module 330 is configured to query the singleinstance storage module 321 for instance of a user ID associated with auser account 316 a, 316 b, 316 c to determine if the user or associateduser account 316 a, 316 b, 316 c is identified in a share list 319 a,319 b for an available message 317 a, 317 b. As shown, the first sharelist 319 a identifies the first, second, and third user accounts 316 a,316 b, 316 c and the second share list 319 b identifies the first andsecond user accounts 316 a, 316 b. The second user communication device314 b is shown communicating with the message database server 310 viathe share module 330 of the communication interface 313. The sharemodule 330 or other system component may verify an account associatedwith the second user communication device 314 b or a user withidentifying data, e.g., username and password, of the second useraccount 316 b. Here, the second user communication device 314 b isverified as being associated with second user account 316 b. The sharemodule 330 is configured to check the second user account 316 b foravailable messages 317 a, 317 b against the share lists 319 a. 319 b.This operation may be performed prior to access, e.g., by generation ofmessage references 317 a′, 317 b′ that the second user communicationdevice 314 b may view via the share module 330. The second usercommunication device 314 b my request or click on the message reference317 a′, 317 b′ to access either single instance message 317 a, 317 b andperform messaging actions according the privilege level orauthorizations specified in the respective share list 319 a, 319 b foreach message 317 a, 317 b.

User communication devices 314 a, 314 b may include or be configured torun, interface, or display a user messaging application 335 configuredto interface with the message database server 310 at the communicationinterface 321. The messaging application 335 a, 335 b may be configuredto provide messaging communication via the user communication device 314a, 314 b with the message database server 310. The messaging application335 a, 335 b may comprise instructions stored in an electronic storagemedium configured to store a set of executable instructions that whenexecuted on the message database server 310 run or simulate themessaging application 335 a, 335 b on the user communication device 314a, 314 b. In various embodiments, the first user communication device314 a may upload the first or second share lists 319 a, 319 b or amodified first and second share list (not shown) to replace the firstand second share list 319 a, 319 b to the message database server 310 atthe same time or subsequent to uploading the first and second message317 a, 317 b. The first user communication device 314 a may provideidentifying information to log onto the system 300, which may bereferred to herein as logging into the associated user account 314 a ofthe user communication device 314 a or messaging application 335 a. Aportion of the identifying information may be provided by identifyinginformation related to the first messaging application 335 a or thefirst user communication device 314 a to associate the first messagingapplication 335 a or device 314 a with the user account 314 a. Ausername or password may also be required to be entered into themessaging application 335 for user verification.

In one embodiment, the first user communication device 314 a isconfigured via the first application program 335 a to indicate one ormore stored share lists 319 a, 319 b to apply to or associate with theuploaded message 317 a, 317 b. The stored shared lists 319 a, 319 b maybe previously defined lists available for quick application to a message317 a, 317 b. The upload module 325 may be configured to receivemessages 317 a, 317 b and share lists 319 a, 319 b from user accounts316 a, 316 b, 316 c, e.g., via the first user communication device 314 alogged into the application 335, system 300, or otherwise authenticatedas associated with a user account 316 a, 316 b, 316 c. In oneembodiment, the second user device 314 b may be configured to query fornotifications of share lists 319 a, 319 b in which the associated seconduser account 316 b, e.g., associated via identifying information, isidentified or authorized to access or share messages 317 a, 317 b. Insome embodiments, notifications may also be sent to the second usercommunication device 314 b or messaging application 335 b, to providenotification of share lists 319 a, 319 b identifying the associatedsecond user account 316 b. Upon verification, the second usercommunication device 314 b may access its associated second user account316 b to perform messaging actions, e.g., using the share module 330, toview, create, send, edit, or delete messages in which the second useraccount 314 b has been authorized to access or share according to theauthorizations and privileges specified in the associated share list 319a, 319 b. Thus, in FIG. 3 , the second user account 314 b has beenidentified as authorized to share the first and second messages 317 a,317 b and may do so using the second user communication device 314 baccording to the specifications provided in the respective first andsecond share lists 319 a, 319 b granting that authority.

In various embodiments, the first user communication device 314 a mayuse the first messaging application 335 a to generate the first andsecond share lists 319 a, 319 b associated with the respective first andsecond messages 317 a, 317 b. Each share list 319 a, 319 b may provide alist of one or more users, e.g., userIDs, user accounts 316 a, 316 b,316 c, or user communication devices 314 a, 314 b authorized to view themessage 317 a, 317 b. The share list 319 a, 319 b may also provide alist of one or more users authorized to modify the message 317 a, 317 b,e.g., edit, add, or delete. The user, via the first user communicationdevice 314 a, may communicate the message 317 a, 317 b and the sharelist 319 a, 319 b via the upload module 325 with the message databaseserver 310. It is to be appreciated that, in some embodiments, the usermay compose or draft messages 317 a, 317 b or share lists 319 a, 319 bpartially or entirely through the messaging application 335 a, 335 bsuch that the first user communication device 314 a does not store themessage 317 a, 317 b or share list 319 a, 319 b. Thus, the messagingapplication 335 a, 335 b may be configured to hide, block, or obscurethe message 317 a, 317 b from permanent or persistent data storageprocesses with respect to the user communication device 314 a, 314 b.

In one embodiment, read, edit, or delete receipts or notifications maybe provided to all or some of the users identified in a share list 319a, 319 b. In one embodiment, users may log onto their account 316 a, 316b, 316 c and receive notifications or query the database server 310,e.g., the share module 330, for messages 317 a, 317 b even beforereceiving a notification or alert. The message 317 a, 317 b may beviewed by authorized users but is not stored on any user or authorcommunication device 314 a, 314 b. After a specified period of time themessage 317 a, 317 b may be deleted automatically if the message 317 a,317 b has not already been deleted by either the author or a specifiedrecipient. In some embodiments, the message database server 310comprises a retention module 337. The retention module 337 is configuredto perform various maintenance operations. For example, the retentionmodule 337 may be configured to retain the message 317 a, 317 b as asingle instance in the single instance storage module 321 until themessage 317 a, 317 b is to be deleted, at which time the retentionmodule 337 may delete the message 317 a, 317 b from the message databaseserver 310.

In certain embodiments, the retention module 337 may further performvarious cleaning functions, such as deleting share list data orcleansing the message database server 310 of notification data. In atleast one embodiment, the retention module is configured to perform adata wipe, not merely an overwrite, operation to completely removemessage data or identifying data. As described above, the share list 319a, 319 b may identify a period of time in which the message 317 a, 317 bis to be available or when the message 317 a, 317 b is to be deleted,e.g., after a specified number of views or after all the one or moresecond users have viewed the message 317 a, 317 b. In some instances,the share list 319 a, 319 b may also identify or associate modificationprivileges to the first user as well as one or more second users thatmay comprise authorization to delete the message 317 a, 317 b at will,at, before, or after a specified time or period of time, after a certainnumber of views or modifications, etc. Thus, when the message 317 a, 317b is called to be deleted in accordance with the share list 319 a, 319 bprivileges or directives, the retention module 337 may delete or wipethe message 317 a, 317 b from the message database server 310 messagingdata and clean the server of references, pointers, notifications, orshare list data. In various embodiments, the share module 330 may beconfigured to communicate with the single instance storage module 321 todelete messages 317 a, 317 b as specified by share lists 319 a, 319 b orthe single instance storage module 321 may be configured to perform theabove operations described above with respect to the retention module337.

FIG. 4 schematically illustrates a further embodiment of a messagingsystem 400 wherein the communication interface 413 comprises a sharemodule 430 that includes a notification module 440. The messaging system400 may include all or some of the elements described above with respectto systems 100, 200, 300 and elsewhere unless stated otherwise. Variousembodiments of the communication interface module 413 are suitable foruse in messaging systems 100, 200, 300. It is to be appreciated that thevarious functionalities described herein with respect to the variousmodules may be shared by multiple modules associated with the messagedatabase server 410, user communication device 414 or application 435,or combinations thereof. The notification module 440 may generate anotification 442 to one or more users identified in a share list 419that a message 417 may be accessed. In one embodiment, all identifiedusers are notified. Notifications 442 may include notifications that anotification 442 or message is available, which may be associated with achange or modification of a message or message privileges or theavailability of a new or updated message. The notification 442 may beprovided periodically, when a share list 419 is received identifying amessage 417 is ready, or at other times determined by the system 400 orwhich may be provided in the user account 416 preferences.

In various embodiments, the share module 430 comprises a message accessportal configured to link or otherwise provide the user with access tomessages 417 stored as single instances in the single instance storagemodule 421. The link may be provided through the user account 416 orthrough the share module 430 from the single instance storage module421. The message access portal may be integrated with the share module430 and may allow the user to view, modify, or take additional messagingactions with respect to the message 417. The actions the user isauthorized to take are generally defined by the privileges specified inthe share list 419. For example, the modification privileges may includeediting privileges, deletion privileges, additional sharing orinvitation privileges. The user that uploads the message 417 and sharelist 419 may choose to retain modification privileges, e.g., to modifythe message 417 or share list 419 to modify the additional users inwhich the message 417 may be shared and the privileges associatedtherewith. However, in various embodiments, the user may set orselectively delegate modification or other privileges in anycombination.

User accounts 416 may include notification preferences defined by users,as introduced above. Users may also provide the message database server410 with one or more electronic addresses in which notifications 442 maybe routed for delivery. The users may add or modify notificationpreferences which may be associated with the user. The preferences maybe stored in the account data module 415 of the message database server410 or on the user communication device 414 and made available throughoperation of the messaging application 435. For example, a user mayindicate a preference to be notified of a notification 442 or message417 at a particular electronic address or a particular electronicdevice. The user may also indicate how notifications 442 are to bepresented. For example, the user may set a preference that messages 417from certain users or notifications 442 thereof may be presented in afirst manner while messages 417 from other users or notifications 442thereof may be presented in a second, third, or additional manner. Theelectronic address may be associated with a particular usercommunication device 414 or may be an account, such as a text messaging,email, social networking, etc. account that may be accessed frommultiple user communication devices. The user may similarly indicate apreference for notifications 442 to be delivered as above but which maydirectly link the user to access the message 417 via the messagingaccess portal, rather than requiring the user to separately access theuser's account 416 on the message database server 410.

In some embodiments, the messaging application 435 or the messagedatabase server 410 via the notification module 440 may encode, morph,or translate the notification 442 in such a way as to obviate the truenature of the notification 442 to those that may view, hear, feel, orotherwise perceive the notification 442. For example, the user mayprovide preferences regarding presentation and receipt of notifications442 defining how notifications are to be translated into a crypticnotification 442, e.g., disguised as an in-operation event, in which theuser may decipher but which others may not. As explained in more detailbelow, the notifications 442 may be obviated in such a way that thenotifications 442 are integrated into or simulated as a normal orubiquitous device function or operation in such a way that such anin-operation notification 442′ will be perceived by others as unrelatedto a message notification 442. For example, the notification 442 may bean in-operation notification 442′ that cloaks the notification 442 as anin-operation event of a secondary function or operation that is notperceived by unintended recipients to be the notification 442.

In various embodiments, the notification module 440 may deliver thenotifications 442 to user accounts 416. In one embodiment, thenotification module 440 may deliver a notification 442 to a user via theuser communication device 414 identified by the user as an approved orauthorized user communication device 414 to receive notifications 442,e.g., according to notification preferences associated with the useraccount 416. The notification 442 may be a notification 442 of thepresence of a notification 442 or reference in the user's account 416 ora notification 442 of a message 417, which may include message details.In some embodiments, the notification module 440 may not providenotifications 442 to a user communication device 414 but rather may beconfigured to maintain a listing of generated notifications 442, e.g.,by message ID, userID, that may be queried. The listing may furtherinclude reference to the share list 419 or message details, such asmessage privileges and settings. It is to be appreciated that, in someembodiments, the notification module 440 may deliver notifications aswell as generate a notification listing that may be queried by thesystem 400, e.g., by the share module 430, user communication device414, or user accounts 416.

In various embodiments, the notification module 440 may be configured togenerate and transmit notifications 442 to user communication devices414 according to the predefined notification settings of each useraccount 416 or communication device 414. For example, the notificationsettings may be predefined with respect to one or more of time of day,manner or route of presentation, user communication device, electronicaddress, as well as combinations of the above. The notification settingmay also predefine if notifications 442 should be automaticallydelivered, delivered only when the messaging application 435 or device414 is in a particular mode, or delivered only when requested by theuser account via the messaging application 435. The messagingapplication 435 may query the notification module 440, share module 430,or a query module, depending on the configuration and which module ispresent and assigned to respond to the messaging application 435. Typeand manner of presentation notifications 442 may be modified by theinteractions between the messaging application 435 and message databaseserver 410 according to preferences provided by the user.

In various embodiments, the share module 430, or, in some instances, theuser communication device 414 or message application 435 comprises aquery module. In one embodiment, both the messaging application 435 andthe share module 430 comprise a query module to interface the two sidesof the system 400 to provide notification 442 of messages 417. The querymodule may be in addition to or instead of the notification module 440.The query module may be configured to query the notification module 440or user accounts 416 for available notifications 440 or links tomessages 417 stored in the single instance storage module 421. The querymodule may be configured to interface or otherwise communicate with theuser communication device 417 via the messaging application 435 toperform query operations. The user may provide identifying information,such as a password, to access the messaging application 435, which mayfurther allow the user to access the user's account 416, e.g., log ontothe user's account. Once logged in, the user may check to see if anynotifications 442 have been generated or delivered to the account. Inone embodiment, the query module is configured to query the singleinstance storage module 421 for a user ID or account associated withmessages 417 stored in the single instance storage module 421.

FIG. 5 schematically illustrates a further embodiment of a messagingsystem 500 wherein the messaging application 535 includes a query module545. The messaging system 500 may include all or some of the featuresdescribed above with respect to systems 100, 200, 300, 400 unless statedotherwise. Similar features are also identified with similar numbers. Itis to be appreciated that while the query module 545 is illustrated tobe associated with the messaging application 535 programed or configuredto be run on the user communication device 514, in some embodiments themessaging application 535 is configured to communicate with the querymodule 545 wherein the query module 545 is a component of the messagedatabase server 510, e.g., with the communication interface 513 andconfigured to query the share module 530, the single instance storagemodule 521, or user accounts 516. Upon being queried 546, the sharemodule 530 of database server 510, e.g., a portion of the moduleconfigured to query for notifications 542, messages 517, or share lists519 identifying the user account 516 associated with the usercommunication device 514 initiating the query 546, is configured tocheck the user account 516 being queried 546 against records or sharelists 519 in the message database server 510. The messaging program 535or the user account 516 may be configured to periodically orspecifically query 546 the message database server 510. In oneembodiment, the user may selectively initiate the query module 530 toquery 546 the system 500 and may provide parameters, e.g., duration ofavailability of message 517, privilege level, newly added or modified,messages 517 authored by the user or another specified user, or othermessage characteristic, to limit the query to a defined set of messages.517. If any messages 517 are available, the database server 510, e.g.,via the share module 530 or an associated query or notificationfunction, may provide notification 542 to alert the user of the message517 in response to the query 546. In some embodiments, upon receivingthe notification 542, messaging application may modify, translate, ormorph the notification 542 for presentation of the notification 542′ tothe user, which may be obscured for interpretation by a specified useras described herein if query 546 was initiated by a background function.Upon receiving and properly interpreting the notification 542′, to benotification 542 of an available message 517, the user specified maythen access the database server 510 to view or act upon the message 517.

In various embodiments, the messaging application 535 installed on orsimulated on the user communication device 514 may be used tocommunicate with the query module 545 to query 546 the message databaseserver 510, e.g., the notification module 540 or user account 516, tocheck for notifications 542 or messages 517 identifying the user. In oneembodiment, the query module 545 may provide references to notifications542 or messages 517 which may route the user to a notification 442 inthe user's account 416 or may provide access to the message 417, e.g.,via the message access portal.

In one embodiment, the user may use the user communication device 514 tocommunicate with the message database server 510 and provide identifyinginformation to log onto the message database server 510 or their account516 to receive notifications 542. The notification 542 may prove a linkthat the user may follow to access via the message access portal of theshare module 530 the message 517 stored as a single instance message 517in the single instance storage module 521. Delivery of a messagenotification 542 to a second user may require that the second user loginto the user's account 516. This may be done via the user messagingapplication 535 stored on the user communication device 514 or by usingthe user communication device 514 to access the account 516, e.g.,through a network or website. For example, the second user may log ontothe user messaging application 5335 installed on the user communicationdevice 514. In some embodiments, the notification module may provide thenotification 542 to the application 535 without the application 535querying 542 via the querying module 545, e.g., when the user hasidentified the electronic address of the user communication device 514for receiving notifications 542. The application 535 may then presentthe notification 542′ to the user, e.g., according to a notificationpreference.

In some embodiments, the message database server 510 is not configuredto provide notifications 542 directly to user communication devices 514,rather user communication devices 514 must initiate communication withthe message database server 510 via the messaging application 535 toaccess a notification 542, e.g., notifications 542 may be delivered tothe user account 516 or the user account 516 may be configured to query546 the message database server 510 to check for message notifications542, updates, or messages 517 available for access. In one embodiment,the user may use the user communication device 514 and messagingapplication 535 to initiate the query 546 or set preferences withrespect to when the user account 516 or user application 535 initiatesthe query module 545 to query 546 the message database server 510.

In one embodiment, the messaging application 545 comprises a backgroundprogram in which the user may initiate revelation of the prompt byperforming an action. For example, the user may tap a sequence of imagesor menus or portion of a screen associated with the user communicationdevice 514 to reveal the prompt. In one embodiment, the messagingapplication 545 may use an accelerometer or other positioning ororientation perceiving components associated with the user communicationdevice 514 to define the action. For example, the user may tilt ororient the user communication device 514 in a predefined manner toreveal the prompt. In some embodiments, combinations of tapping andorientating may be used to reveal the prompt. In one embodiment, theuser may define the actions that may be performed to reveal the prompt.For example, the user may define a particular sequence of actionsconfigured to reveal the prompt. In one embodiment, the user may performa series of touches or outlines, to, e.g., draw a shape or design thatwill reveal the prompt. Similarly, in one embodiment, a password maycomprise a particular sequence of actions as described herein.

FIG. 6 schematically illustrates one embodiment of a messagingapplication 635 suitable for operation in the messaging systemsdescribed herein. The messaging application 635 comprises a primarymessaging function 650 and a secondary function 652. The secondaryfunction 652 is configured to appear as and otherwise function as anapplication or operation associated with the user communication device614 that is not the messaging function 650. Typically the secondaryfunction 652 is presented and operates as a typical or ubiquitous typeapplication that would be expected to be on or associated with the usercommunication device 614, such as a map function, typical messagingfunction, settings or configurations, games, debugger, mobileapplications, etc. The secondary function 652, however, may beintegrated with the primary messaging function 650 of the messagingapplication 635 to, for example, provide notifications 642/642′ to theuser during operation of the secondary function 652. For example, themessaging application 635 may translate or morph a notification 642 of amessage or message data details into a notification 642′ that isobscured or presented in a cryptic manner, which may be defined in partby user preferences, that may otherwise be perceived as an in-operationevent associated with the second function 652 or operation of the usercommunication device 614 or its associated functions that are unrelatedto a message notification 642. The messaging application 635 includes aquery module 645 to query 646 for messages, notifications 642, or toreceive notifications 642 from the message database server 610, whichmay be similar to message database servers 110, 210, 310, 410, 510. Themessaging application 635 also includes a notification module 640configured to receive notifications 642 from the query module 635 or themessage database server 610, e.g., from a share or notification moduleassociated with the message database server 610, and to providenotifications 642/642′ as provided in the preferences. When thenotification module 640 provides notifications 642 while the messagingapplication is in a stand-by or secondary function mode, thenotification module 640 is configured to present an in-operation orobscured notification 642′ that obscures the true meaning of thenotification 642. It is to be appreciated that in some embodiments, themessaging application does not include a query module or notificationmodule and may be configured to communicate with a notification moduleor a query module associated with the database server 610. For example,in one embodiment, the messaging application 635 includes a notificationmodule 640 configured to receive notifications 642 from a notificationmodule associated with the database server 610 and present thenotification 642 as an in-operation or obscure notification 642′associated with the secondary function 652.

In various embodiments, the notification 642′ may comprise an eventassociated with the user communication device 614 or operation thereof,e.g., the secondary function 652. Upon receiving the notification 642,the user may log onto or otherwise access the user's account to viewmore details about the notification 642 or access the message via themessage access portal of the share module. Thus, in one embodiment,notifications 642 may be sent to a user communication device 614 andpresented to the user as a predefined and cryptic notification 642′. Forexample, the notification 642′ may be presented in the secondaryfunction 652 of the application 635 as a sound, display, image,vibration, movement, or other event, etc. that appears to be associatedwith the secondary function 652 in order to obscure the notification 642so as to not indicate a new message but that an event related to thesecondary function 652 is available or happened. In various embodiments,the events associated with the secondary function 652 used to providecryptic notifications 642′ may be customized by the user, e.g., viapreferences associated with the user account.

As described in more detail below, the notification 642 may be obscuredor cryptic such that only those able to decipher the notification 642′will realize that the notification 642 is present or the true nature ofthe notification 642′. In certain embodiments, notifications 642/642′may include additional details with respect to the message, such asidentification of the first user, additional second users that mayaccess the message, modification privileges, time period the message hasbeen or will be available prior to deletion, number of modifications,etc. Notably, in some embodiments, such information may not beassociated with the notification 642/642′ or may be associated with anotification available upon accessing the user's account on the messagedatabase server 610. In some embodiments, the notification 642′, whichmay include message details, may be presented in an encoded manner toobviate the notification or details. That is, the notification 642 ordetails may be presented in the notification 642′ in a manner that theuser may specify or decipher but which others that may perceive thenotification 642′ may not. While the secondary function 652 andmessaging function 650 are typically tied within the same messagingapplication 635, the messaging application 635 could include a messagingfunction 650 and an integration function configured to integrate into anoperation of the communication device 614 such that the operationintegrated becomes the secondary function 652. Thus, in one embodiment,the messaging application comprises an integration function configuredto hijack or morph a portion of another program, application, oroperation to apply customized notifications through the hijackedprogram, application, or operation. Preferably, hijacking does notsignificantly impair the operation of the hijacked program, application,or operation.

FIG. 7 schematically illustrates a messaging application 735 comprisinga messaging function 750 and a game function 752. The game function 752may comprise a secondary function that may be run on the usercommunication device 714 and that is configured to obscure the messagingfunction 750, e.g., the primary messaging function. For example, in oneembodiment, the messaging application 735 may be integrated into a gameapplication that may be run on a user communication device 714.

Within the game function 752 and upon a user action 754 the application735 may be configured to present a login prompt 756. Depending on theconfiguration or preferences, the user action 754 may include opening orinitiating the game function 752, performing a sequence of actions asdescribed herein, and which may or may not be after an in-gamenotification 742′ has been presented, which in some embodiments maychange the actions 754 that must be performed to present the prompt 756.When the user performs the user action 454 correctly 458 the loginprompt 756 is presented. When the user action 754 is not performed orperformed incorrectly 759, the messaging application 759 remains in thegame function 752. The login prompt 756 may be presented to a user torequest that the user provide identifying information, such as ausername or password associated with a user account, to provide accessto the user messaging account. The prompt 756 may be generic in that itdoes not identify the messaging application 735 or may be disguised as aprompt for another application or privilege. If the user provides thecorrect identifying information 760 at the prompt 756, the messagingapplication 735 displays or enters the messaging function 750 whereinthe user may perform the messaging operations such as accessing themessage database server and the user account. If the user is unable toprovide the correct identifying information 761 at the prompt 756, theprompt 756 may disappear and the game function 752 may continue. Thus,if the user provides identifying information associated with a useraccount, which may be linked to the application or the message databaseserver, the messaging function 750 will appear and be fully functional.

The prompt 756 may be configured to appear or be revealed at one or morepredetermined times such as upon initialization of the application,after a first period of time following initialization, or periodically.In one embodiment, the prompt 756 is configured to appear with respectto the game operation, e.g., when a level has been passed or uponperforming another user action 754 or operation related to the secondaryfunction 752, such as initiating and then pausing a song in anembodiment wherein the secondary function comprises a music function orinitiating a clean in an embodiment wherein the secondary functioncomprises a debugging function. In one embodiment, the prompt 756 isconfigured to appear after the user has manipulated a user interfacesuch as one or more buttons, touch, menus, clicks, etc. in a specifiedmanner. For example, a user action 754 may comprise the user correctlyperforming 760 a sequence or series of clicks, taps, or orientations ofthe user communication device 714 to reveal the prompt 756. In anotherembodiment, the user may initiate an operation or perform an actionrelated to the secondary function to reveal the prompt 756.

In one embodiment, the user may exit 762 the messaging function 750 byinitiating a stand-by mode 763 with respect to the messaging application735. For example, the user may tap a user interface such as a touchscreen or button at which time the messaging application 735 ormessaging function 750 may disappear from the screen. In one embodiment,exiting 762 or entering stand-by mode 763 will return the messagingapplication 735 to the game function 752 that the user previouslyinitiated. In some embodiments, while the messaging function 750 of themessaging application 735 exits 763 to stand-by mode 763 or gamefunction 752, the messaging application 735 may periodically querymessage database server, e.g., via communication with the query module,for notifications regarding an available message or if a message isavailable. The query module may query the notification module for anotification or additional notification details. When a notification ofa message is available, the messaging application 735 may provide anotification 742′ to the user as described above.

Thus, the messaging system may include a messaging application 735comprising a messaging function 750 cloaked in a video or game function752. The messaging application 735 is configured to cloak the messagingfunction 750 and notifications 742′ such that unintended recipient arenot aware of the messaging function 750 or the true meaning of thenotification 742′ or even that a notification 742′ is a notification.Thus, some of the messaging functions 750 may be integrated into thegame functions 752 to therefore utilize, for example, a fully functionalmobile game application in order to obscure the primary messagingfunctions of the messaging application 735. In one embodiment, withinthe game function 752 of the functional game of the messagingapplication 735, performing a user action 754 comprising correctly 758tapping a series of menus will reveal a login prompt 756. Upon enteringan incorrect 761 username or password, the prompt 756 may disappear andthe game function 752 of the application may continue to function. Butwhen a correct 760 username and password combination is entered, themessaging functions 750 of the application 735 appear and are fullyfunctional.

In one embodiment, when the user taps or clicks a stand-by or log offbutton 763, the messaging function 750 disappears and the user may thenreturn to the game function 752 of the messaging application 735 thatthe user started with. While in stand-by mode 763 the messagingfunctions may periodically query the database server for a message ornotification. These messaging functions 750 may perform the querying inthe background while the game function 752 or other device operation ison-going. Thus, the user of the communication device 714 may be unawareof the query operations. When a message is available, an in-gamenotification 742′ will be presented, e.g., a sound and/or vibration willoccur. Unless the user is the intended recipient, the user may notperceive or be able to decipher that the in-game notification 742′ is anotification of a message and may assume the in-game notification 742′,e.g., a sound, display, image, vibration, movement, or other event,etc., is simply a notification of a game event or the occurrence of agame event. Thus, the in-game notification 742′ may be designed to beobscured so as to not indicate a new message but rather that a gameevent is available or happened. In various embodiments, in-gamenotifications 742′ may be customized by the user. For example, a usermay specify game events to be used as in-game notifications 742′ to, forexample, indicate which author uploaded the message. The type of gameevents used for in-game notifications 742′ may further be customizableby the user to provide notification details. For example, an in-gamenotification 742′ may be a background, theme, or image change thatindicates that a message from a specific first user or generic firstuser is accessible by the user. Other details, such as time the messageis available, modification privileges, etc. may similarly be presentedin the in-game notifications 742′. In various embodiments, the in-gamenotifications 742′ may comprise sounds such as songs, beats, phrases,music, or chimes, themes, background images or scenery, bonus points,extra lives, appearance or availability of additional features, e.g.,power-up available, perspective or view change, character or imagechanges, e.g., game character changes size, color, or appearance,performance change, e.g., character can run faster, fly, see throughwalls, or throw fire, increased options, e.g., new weapons areavailable, a game character appears or performs an identifiable action,e.g., character spins, dances, or an antagonist or assistant appears. Inone embodiment, a new level or portal to a new or different level orstage appears in which selection or attempt to enter the level revealsto the prompt 756 to access the messaging function 752 where the messagemay be accessed. As above, if the incorrect 761 identifying informationis entered, the user will return to the game function 752, however,depending on the embodiment, the user may not be able to advance to thenew or additional level. This may further disguise the prompt 756.

FIGS. 8A-8C schematically illustrate portions of a password resetfunction 863 according to various embodiments. The password resetfunction 863 may enable a user to reset a password associated with theuser account using a temporary password 864, e.g., if the user hasforgotten the current password 867 or if the user believes the currentpassword 867 may be compromised. In FIG. 8A, the user initiates thepassword reset function 863 by submitting a request 865 to the system800. The system 800 responds by providing 866 a temporary password 864.In this embodiment, the existence of the temporary password 864 does notterminate authenticity or functionality of the current password 867, asshown in FIG. 8B. Thus, the current password 867 remains operative toaccess the user account when the user attempts to log into 868 the useraccount 816. However, in one embodiment, by entering the currentpassword 867 to log into 868 the user account 816 before using thetemporary password 864 to log into 869 the user account 816 willinvalidate the temporary password 864 such that the temporary password864 may not be used to log into 869 the user account 816. As shown inFIG. 8C, if the user uses the temporary password 864 to log into 869 theuser account 816 before the user uses the current password 867 to loginto 868 the user account 816, the temporary password 864 is invalidatedand the system 800 is configured to revert 899 b the user account 816 toan original state 816′, e.g., all personalized or customized settings orpreferences and information are deleted 899 a and may not be recovered.

In various embodiments, the communication interface of the messagedatabase server includes a network interface, web page, or website thatmay be used to interface with the message database server. Thecommunication interface may include a static or dynamic web pageconfigured to interface with a user communication device, e.g., with abrowser or application, which in some embodiments may be associated withor include the user messaging application. A user or prospective usermay access the web page via the user communication device. The usercommunication device may include the user messaging application, whichmay be provided in various forms, such as a mobile application orpersonal computer application that may include browser functionalities.In one embodiment, the user may download the user messaging applicationonto the user communication device directly from the web page, onlinestore, or a tangible storage medium. In one embodiment, the usermessaging application may be available for virtual operation on the usercommunication device through the communication interface of the messagedatabase server.

FIG. 9 is a navigation diagram of a website interface 970 for use withthe messaging system according to various embodiments. The website 970includes a navigable collection of pages that may be accessed anddisplayed on the user communication device for interfacing with themessage database server. Initially, a user or potential user may accessa login or home page 971 including a graphical user interface. At thelogin page 971, the user may sign up for an account by selecting aregistration link 972. When the registration link 972 is selected, theuser may be provided with a registration form. The user may be requiredto complete portions of the form to initiate or complete registration.Once registered, a user account may be created for the user. Whencreating a user account, the messaging system may assign or requestaccount identification or access data from the user. For example, theuser may be required to create or select a username and password that isto be provided upon login 971 or at the login prompt as described above.In some embodiments, the user may further or optionally provide aphysical or electronic address, such as an email address. The addressmay allow recovery of forgotten passwords or usernames, e.g., allowingthe user to receive a temporary password upon request. Thus, in someinstances, the absence of an address or other route of contact orverification may prevent recovery of forgotten passwords or usernames.In one embodiment, a user that has forgotten a password may select therecovery link 973 on the login page 971 wherein the user will bepresented with a recovery form for completion. For example, the user mayrequest that the message database server send a temporary password to anemail address, if one was previously provided or on file. In someembodiments, the absence of an email address record prevents resettingof the password. In one embodiment, the recovery form may include fieldsfor username or email address. If the username is found with an emailaddress on file then a temporary password will be sent. In oneembodiment, if the provided email address is found on file, the usernameand a temporary password may be sent. If the username is found withoutan email address on file, no temporary password will be sent. In variousembodiments, additional measures may be taken to prevent those havingunauthorized access to a user's email account from obtaining access tothe user's identifying information to access the account. For example,the user may be required to answer one or more pre-determined challengequestions to recover a password. In some embodiments, if a temporarypassword is used, the user's account is reverted to its original stateand all messages and contacts are deleted from the user's account. Invarious embodiments, the login page 971 includes various informativelinks 974 descriptive of the website and its policies such as an aboutlink, a frequently asked questions link, or a privacy or terms ofservices link and a contact link wherein the user may complete a contactform to contact site administrators, owners, or the like.

When the user has successfully logged onto the website, the user mayaccess various aspects of their account by navigating one or more webpages. Once logged into the system, the user may link with a new messageform 975 into which a new message may be composed, a message detailspage 976 to view messages and link to a conversation page 976 a, acontacts page or address book 977 to view contacts, or an accountinformation or settings page 978. The account information or settingspage 978 includes a payment section 978 a having a payment form 981 a.The account information or settings page 978 also includes a changeUserID/password section 978 b requiring the user to complete a changeform 981 b. In some instances, the change UserID/password section 978 bmay include a link to the payment section 978 a requiring the user tocomplete the payment form 981 a for processing the changeUserID/password. The account information or settings page 978 alsoincludes a stand-by mode setting section 978 c for providing preferencesand settings for stand-by mode. The account information or settings page978 also includes a block/white (VIP) list settings section 978 dallowing the user to customize their address book or contacts byblocking or blacklisting users in which the user has blocked messaging.Similarly, the block/white (VIP) list settings section 978 d allows theuser to identify white list or VIP users that enjoy preference. Such VIPusers may be assigned different notifications, priority listings in thecontacts and messages pages, or other preferential status allowing theuser to receive and respond efficiently to messages from the listed VIPusers. The account information or settings page 978 also includes asubscription status section 978 e allowing the user to view subscriptionstatus, receive special offers for update, renewing, or upgrading theircurrent subscription. In some embodiments, subscription histories mayalso be available including past reversions of their account to itsoriginal state as well as limited recovery points to recover previousaccount settings prior to changes initiated by the user. Links 980 arealso provided in the internal pages for quick access to the accountinformation page 978, payment forms 981, and logging out 972. Links forside navigation to internal pages 982 may include an inbox link 982 athat directs to the message details page 976, a contacts link 982 b thatdirects to the contacts or address book page 977, a block list link 982c that directs to contacts or address book page filtered to show onlyblocked or blacklisted contacts, and a list of conversations link 982 dthat directs to a page listing all conversations that contain at leastone message.

FIG. 10 illustrates features of a message details page 976 according tovarious embodiments. The message details page 976 provides a view ofmessages which the user is authorized to access. In some embodiments,the messages may be sortable by the UserID of the author or usersauthorized to view the message in the first column 983 a, the datecreated, last edited, most recently viewed, unviewed, pending, or bydate specified for being deleted 983 b in the third column, for example.A short preview of the message is provided in the second column 983 c.In various embodiments, unread messages may be indicated by a bold orconspicuous type formatting. Messages may also be deleted from themessage page 979 by selecting a box 983 d adjacent to the message tomark for the message for deletion. Selecting a message takes the user tothe message or conversation page 976 a specific for the message andincludes the message and related conversations. The conversation page976 a also includes an input field for writing a new message. Links 980are also provided at the top of the message page 979 for quick access tothe account information page 978, payment forms 981, and logging out972. A search box 984 is also provided at the top of the page to allowthe user to search their account or the website 970. Side navigationlinks 985 are provided to provide quick links including an inbox link985 a, an important messages link 985 b, a sent messages link 985 c, adraft message link 985 d, a contacts link 985 e that directs to thecontacts or address book page 977, and a black list link 982 f thatdirects to contacts or address book page filtered to show only blockedor blacklisted contacts. A compose link 986 is also provided to directthe user to a new message form 975 from which a new message may becomposed.

FIG. 11 illustrates features of a contacts page 977 according to variousembodiments. The contacts page 977 provides a view of the user'scontacts. In some embodiments, the contacts may be sortable by thecontact name or UserID in the first column 977 b alphabetically or by arating system that the user may use to prioritize their contacts, e.g.,favorite, date added, groups, subscription level, most used, etc. Thesecond column 977 c provides contact information such as a phone number.The third column 977 d is available for other information related to thecontact such as comments, number of messages open, notes, or whateverthe user chooses to use the column 977 d for. In this instance, the userhas chosen to use the third column for email addresses. In someembodiments, the contacts page 977 may include customizable featuresallowing the user to add additional columns for information that mayallow the user to quickly and accurately sort through the contacts.Contacts may be removed or added to the white or VIP list and in someinstances removed or added to the black or block list by selecting a box977 a adjacent to the contact to mark the promotion or demotion of thecontact. In one embodiment, addition or removal from one contacts listmay initiate an optional notification to the contact of the change. Inone instance, the notification may include removing the first user fromthe contacts page 977 of second users in which the first user hasblacklisted. In another embodiment, the notification may includehighlighting or presenting the first user in a conspicuous color or fontin the second user's contacts page 977. Links 980 are also provided atthe top of the message page 979 for quick access to the accountinformation page 978, payment forms 981, and logging out 972. A searchbox 984 is also provided at the top of the page to allow the user tosearch their account or the website 970. Side navigation links 985 areprovided to provide quick links including an inbox link 985 a, animportant messages link 985 b, a sent messages link 985 c, a draftmessage link 985 d, a contacts link 985 e that directs to the contactsor address book page 977, and a black list link 982 f that directs tocontacts or address book page filtered to show only blocked orblacklisted contacts. A compose link 986 is also provided to direct theuser to a new message form 975 from which a new message may be composed.

FIG. 12 illustrates features of an account information or settings page978 according to various embodiments. The account information orsettings page 978 includes the change UserID/password section 978 b.This section may provide information regarding the strength of thecurrent password or a history of the current password or previouspasswords. If the user wishes to change their ID or password, the usermay be directed to a change form 981 b in which to request the change.In some embodiments, the change UserID/password section 978 b mayinclude a link to the payment section 978 a requiring the user tocomplete the payment form 981 a for processing the request to changetheir user ID. Preferably a fee processed through the payment forms 981a is required for changing username/userID, however, changes topasswords are typically not accompanied by a fee. In some embodiments,changing a user ID updates instances of the user ID in the contactlistings of other users. The account information or settings page 978also includes a default time section 978 f for specifying a default timeat dropdown menu 981 c and default langue section 978 g selectable indropdown menu 981 d. In certain embodiments, selecting a defaultlanguage initiates a translation services, such as a machine translationservice, for translation of messages into the selected default language.Thus, the system may allow users that speak different languages toexchange messages using different default languages. The payment section978 a allows the user to make payments related to their account, e.g.,payments for their subscription or to other users. A dropdown menu 981 amay be used to identify the correct type of payment and form. Theaccount information or settings page 978 also includes the stand-by modesetting section 978 c for providing preferences and settingsnotifications in stand-by mode. Here, the user has chosen to receiveactivity notifications. In some embodiments, the website may furtherallow the user to select messaging application notification preferenceswhen the application is linked to the account. Alternately, themessaging application may retain preferences with respect toin-operation notifications and related customizations. The user is alsoprovided with a panic button section 978 h allowing the user to disableor enable a panic button feature when the user account is configuredwith a messaging application that the system identifies with the user,e.g., by a device or application ID. The account information or settingspage 978 also includes the block/white (VIP) list settings section 978 dallowing the user to enable or disable white list only to allow onlyusers from the user's white list to see the user as a contact and beable to contact the user. The account information or settings page 978also includes the subscription status section 978 e allowing the user toview subscription status. Links 980 are also provided at the top of themessage page 979 for quick access to the account information page 978,payment forms 981, and logging out 972. A search box 984 is alsoprovided at the top of the page to allow the user to search theiraccount or the website 970. Side navigation links 985 are provided toprovide quick links including an inbox link 985 a, an important messageslink 985 b, a sent messages link 985 c, a draft message link 985 d, acontacts link 985 e that directs to the contacts or address book page977, and a black list link 982 f that directs to contacts or addressbook page filtered to show only blocked or blacklisted contacts. Acompose link 986 is also provided to direct the user to a new messageform 975 from which a new message may be composed.

According to various embodiments, the website 970 includes a mobiledevice website requiring simplified rendering and processing to allowusers to access the service in a mobile friendly environment using amobile device, e.g., Android/iOS systems. The user may access the mobilewebsite version by logging in at the login page 971 by providing ausername and password. When the user has successfully logged onto themobile website, the user may access the messaging details page 976 toselect messages to read, send, or delete message. The user may alsoaccess their account contacts in their address book 977 to performupdates to their contacts including inserting, updating, and deletingcontacts. The user may also update or modify their block list availablethrough block list link 985 f to insert new blocked contacts or updateor delete blocked contacts. The user may also access their accountinformation and settings 978 to update or modify their account settings.In various embodiments, the user may change their password using theUserID/Password section 978 b, preferably for a fee processed throughthe payment forms 981 a. The user may also change their password, whichtypically is not accompanied by a fee. The user may also update ordelete their contact or other identifying information or review past andcurrently processing payments.

FIG. 13 is a navigation diagram of a messaging function or portion 987of a messaging application according to various embodiments. Asdescribed above, the messaging application preferably includes asecondary function such as a game function or integration configured toobscure various messaging functions of the messaging portion. Themessaging application may be configured for user communications devicessuch as mobile phones, tablets, PDAs, personal computers. The messagingfunction 987 is associated with a mobile messaging application. Themessaging function 987 includes a logon section 988. The logon section988 includes a quick uninstall or panic button 989 that allows the userto uninstall the messaging application from the user communicationdevice. In one embodiment, the user does not need to be logged into themessaging portion 987 or the messaging application in order to uninstallthe application. In one embodiment, when the panic button 989 istriggered, the application uninstalled such that removal of theapplication may be accomplished with one click. In the navigationdiagram 987, when the panic button 989 is triggered, the user isprompted 989 a to confirm that the application should be removed. If theuser confirms, the messaging application is removed from the usercommunication device. Confirmation of successful removal of themessaging application from the user communication device may also beconfirmed 989 b.

At the login section 988 the user is required to enter their usernameand password to access the messaging portion 987. In variousembodiments, when the user has previously logged into the messagingfunction, e.g., the messaging application is in stand-by mode, the usermay be required to only enter a password. However, in one embodiment, ifthe user enters an incorrect password, the user is required to enter acorrect username and password to login. When the user has successfullylogged into the messaging portion 987, the user may access a messagedetails section 990 which may be similar to message page 976, a contactssection 991 which may be similar to contacts page 977 and may include aconversation input field section 990 a similar to the conversation withinput field 976 a, a block list section 992 to display only blockedcontacts, a privacy/terms of service section 993, and a logout section994. The messaging section may also include an account information orsettings link 995 to link the user with an account information orsettings section. In the messaging details section 987 the user mayread, send, and delete messages as well as draft messages orconversations 990 a. In the contacts section 991 the user may insert,update, and delete contacts. In the block list section 992, the user mayinsert, update, and delete their block list. In the account informationor setting section available through the account information andsettings link 995 may be similar to account information and settingspage 978 allowing the user to change the username/userID associated withthe account, e.g., for a fee, change the account password, or change orremove identifying information such as an email address. The user maysimilarly modify and define stand-by settings. After completing desiredmessaging activities, the user may logoff the messaging portion 987 ofthe messaging application or enter stand-by mode. In one embodiment, themessaging application provides a link to the mobile website that, whenclicked by the user, opens the mobile browser of the user communicationdevice and links the user communication device to the mobile website.

The user may also indicate that their password has been lost or requesta temporary password at the login section 988 or login page 971 of thewebsite. A password reset function may include sending the user atemporary password, e.g., to an email account, if one was provided withthe user account. In no email is associated with the user account onfile, the password may not be available to be reset. After the temporarypassword has been sent, the user's old password may still be fullyfunctional. However, logging into the user's account with the oldpassword will invalidate the temporary password that was requested. Ifthe user uses the temporary password before the temporary password isinvalidated, the users account will revert back to the original state.For example, in one embodiment, all messages and contacts are deletedwhen a temporary password is used to access a user account. In someembodiments, the deleted data is unrecoverable. In one embodiment, auser may also change a username or even their userID with their useraccount at any time. For example, when the userID and username aredissociated, either may be changed without changing the other. When theuserID and username are the same, changing the username may or may notchange the userID, which may be given as a choice to the user whenrequesting or executing a change. If the userID is changed, the userIDmay also be changed to the updated or new userID in all the addressbooks and block lists of other user accounts including the old userID.

In various embodiments, the user messaging application may be configuredto run continuously or substantially continuously in the background ofthe user communication device. The continuous operation may be for apre-defined period of time that may include periodic continuousoperation that may or may not be determined by another operation of theuser communication device or operation of the user messagingapplication. For example, the user messaging application may beconfigured to run in stand-by as a background process for 24 hourswithout activity after the user chooses a stand-by option. During thestand-by period, the user messaging application may be configured toperiodically communicate with the message database server via thecommunication interface for new messages. In various embodiments, theuser may configure the intervals wherein messages are checked. Forexample, the user may provide a preference in the settings interfacepage from a dropdown menu or in a field. For instance, the user maydefine intervals of once every 1 to 15 minutes or other interval. Suchintervals may be variable or variable with respect to time of day orweek. For example, the user may want the application to check formessages more often at peak times and less often during non-peak times.In one embodiment, the application interface may include a quickrefresh, message check, half-time, double-time, or other time buttonwhereby the user may quickly check or increase or decrease checkintervals.

In one embodiment, if the number of messages is greater than zero, theuser messaging application will notify the user of the new message,e.g., with an identifiable icon in a notification bar, graphic, sound,or pop-up ad, which may be disguised as an in-operation event associatedwith operation of the user communication device or another application.For example, a notification of a new message while in stand-by mayinclude a message delivered from a pseudo text messaging account orapplication wherein the true nature of the notification is disguised inthe message as an innocuous greeting or phrase.

In various embodiments, when the user may choose to completely logout orturn off the message check operation. For example, the user may selectthe logoff button to completely logoff such that the user messagingapplication will not check for messages until the user logs back ontothe message database server, which may be through the user messagingapplication.

The user messaging application may be configured with shorter checkintervals when the user is actively using the application, which mayinclude using the messaging or secondary operations, such as a gainingportion of the user messaging application. For example, in oneembodiment, when the user is actively using the application theapplication may be configured to check for new messages every 10 secondsand notify the user as described herein when new messages is greaterthan zero.

In various embodiments, the user may draft, read, view, edit, or deletemessages through the messaging application. Messages may include variouscommunication formats including text, video, sound, photographs,multi-media, etc. In some embodiments, notifications may be sent when anew message is available to be viewed. In one embodiment, the author or,in some instances, other users via their account may receive anaccounting of prior messaging views. For example, the author of amessage may be presented with a read receipt linked to the message intheir account when one or more users, such as a particular user theauthor specified or any or all users listed in the share list haveviewed the message.

As described above, in various embodiments, while a user account may belinked with a user device via an application or address, for example,the user must first log into the application or their account with useridentification data to authorize or begin receiving notifications. Forexample, a user may log into the application via the user device havingthe application, which in one embodiment may be any user device havingthe application, or onto a designated website or server configured torun the messaging program. The user may then log out of the applicationor their account or place the application in a stand-by mode such thatnotifications may be received on the user device having the applicationauthorized to their account in stand-by mode. The user may also log outof the application while terminating authorization to receivenotifications associated with their user account on the user deviceuntil a later time upon logging into or reauthorizing notifications tobe received to an application or user device. Thus, in one embodiment,the user may use one of a number of user devices to access their useraccount and receive notifications by logging into their user account viathe messaging application or website.

In various embodiments, whatever user device the user is logged into inan active or stand-by mode may enable notifications to be received bythe user device, e.g., logging into the user account via a user devicemay authorized that user device to receive notifications for the useruntil the user logs out or after a period of time, which in someinstances may be selected at log in. For example, a user using a userdevice that others use may choose to indicate that their account shouldautomatically log out from active or stand-by after an hour or otherindicated time. In various embodiments, the database server isconfigured to identify user accounts within the system by uniqueidentifying numbers that users may never see. In one embodiment, theusers may only see username and/or nicknames associated with theiraccount.

In one embodiment, login has three phases or modes. In a first mode, thelogin is active. In this state, the user may access the user account viathe application or website to perform the various messaging operations.The access may be complete account access for performing messagingoperations. In a second mode, login is passive or on stand-by. Forexample, to enter stand-by the user may press a stand-by button orapplication inactivity. The this mode, the user may be able to receivenotifications associated with their user account via the application orwebsite to their user device, e.g., notifications of new messages. Inone embodiment, when in stand-by mode, a user may receive a notificationof a new message and then attempt to enter the application or their useraccount to read the new message. In one instance, the user will berequired to enter a password associated with their account when clickingon a notification, for example. If the user is unable to enter thecorrect password, the application or the user account may prevent theuser from accessing the associated user account or view the message. Inone embodiment, where the application is associated with a game, theapplication may return to the game. In some instances, the applicationmay transition to a third mode or logged out mode, which will requirethat the user enter a username/password combination to reauthorizeaccess to the user account. Thus, in one embodiment, a third modeincludes a logged out mode, in which the previous authorizations withrespect to the application, receiving of notifications to the userdevice or application are revoked such that access to the user accountor notifications requires that the user entre the first mode by enteringa username/password combination to access messaging and notificationaspects of the user account or application.

In various embodiment, the application may be configured to query thedatabase while in stand-by mode at various intervals. In one embodiment,the application queries the database server anywhere from 1 to 15minutes, however, other query intervals may be used. The query intervalsmay be user configurable. While using the application or game, forexample, the application may be configured to query the database serverevery 10 seconds.

In one embodiment, notifications may be presented in a game setting, asdescribed above. The notifications may be disguised as in-game events.In one embodiment, a photo application may be used to receivenotifications. For example, a particular gesture in a photos mayindicate a message. In one embodiment, the application may include aphoto application in which gestures, backgrounds, attire, or images maybe manipulated by touching a user interphase. For example, notificationsmay be linked to a particular change that occurs to the photograph uponmanipulating the photo. In this or another embodiment, logging into orpresentation of the password to receive a notification may be linked toa photo application such that by touching or sliding a finger across aseries of points within a photo the application can become active, e.g.,transitioned from stand-by to active mode.

In various embodiments, the user messaging application and the messagingprogram are configured such that no message are to be saved to a usercommunication device hard drive, permanent or secondary storage mediumbut rather will exist in temporary, volatile, or RAM.

The programs and applications described herein may include instructionssuch as software stored on machine-readable medium embodying any one ormore of the methodologies or functions described herein. Theinstructions may also reside, completely or at least partially, withinthe main memory, the static memory, or within a processor, or acombination thereof, during execution thereof by the system or componentthereof, such as the message database server. Dedicated hardwareimplementations including, but not limited to, application specificintegrated circuits, programmable logic arrays and other hardwaredevices can likewise be constructed to implement the systems describedherein. Applications that may include the apparatus and systems ofvarious embodiments broadly include a variety of electronic and computersystems. Some embodiments implement functions in two or more specificinterconnected hardware modules or devices with related control and datasignals communicated between and through the modules, or as portions ofan application-specific integrated circuit. Thus, the example systemsare applicable to software, firmware, and hardware implementations.Furthermore, software implementations can include, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. The databaseserver may generally include a machine-readable medium. While thedatabase server is generally describe singly, it should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more sets of instructions. The term “machine-readable medium”shall also be taken to include any medium or device that is capable ofstoring, encoding or carrying a set of instructions for execution by themachine and that cause the machine to perform any one or more of thefunctions or methodologies of the present disclosure. Solid-statememories such as a memory card or other package that houses one or moreread-only (non-volatile) memories, random access memories, or otherre-writable (volatile) memories; magneto-optical or optical medium suchas a disk or tape; or other self-contained information archive or set ofarchives is considered a distribution medium equivalent to a tangiblestorage medium may be used. Accordingly, the disclosure is considered toinclude any one or more of a machine-readable medium or a distributionmedium, as listed herein and including art-recognized equivalents andsuccessor media, in which the software implementations herein arestored.

The illustrations of arrangements described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other arrangements will beapparent to those of skill in the art upon reviewing the abovedescription. Other arrangements may be utilized and derived therefrom,such that structural and logical substitutions and changes may be madewithout departing from the scope of this disclosure. Figures are alsomerely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Thus, although specific arrangements have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific arrangementshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments and arrangements of the invention.Combinations of the above arrangements, and other arrangements notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description. Therefore, it is intended thatthe disclosure not be limited to the particular arrangement(s) disclosedas the best mode contemplated for carrying out this invention, but thatthe invention will include all embodiments and arrangements fallingwithin the scope of the appended claims.

The foregoing is provided for purposes of illustrating, explaining, anddescribing embodiments of this invention. Modifications and adaptationsto these embodiments will be apparent to those skilled in the art andmay be made without departing from the scope or spirit of thisinvention. Upon reviewing the aforementioned embodiments, it would beevident to an artisan with ordinary skill in the art that saidembodiments can be modified, reduced, or enhanced without departing fromthe scope and spirit of the claims described below.

What is claimed is:
 1. A messaging system for providing messagingservice between or among user accounts, the messaging system comprising:a message database server comprising memory that stores instructionsthat when executed by a processor cause the message database server toperform operations of an account module, upload module, share module,and a password reset function, wherein the account module is configuredto maintain user accounts, each of the user accounts associated withuser identifying data including a first password required to access theuser account, wherein the upload module is configured to receive messagedata from user communication devices associated with the user accounts,the message data including a message and identification of one or moreof the user accounts maintained by the account module with which themessage is to be shared, wherein the share module is configured to sharethe message with the one or more identified user accounts, and whereinthe password reset function is configured to issue a second password toone of the user accounts upon request, and wherein, when the secondpassword is used to access the user account, the user account reverts toan original state wherein all personalized information, includingpayment information, associated with the user account is deleted andunrecoverable.
 2. The messaging system of claim 1, wherein if the firstpassword is used to access the user account before the second passwordis used to access the user account, the second password is invalidated.3. The messaging system of claim 1, wherein issuance of the secondpassword does not invalidate the first password, wherein use of thefirst password to access the user account before the second password isused to access the user account invalidates the second password, andwherein use of the second password to access the user account before thefirst password is used to access the user account invalidates the firstpassword.
 4. The messaging system of claim 1, wherein the message datacomprises the message and a share list, wherein the share listidentifies the one or more identified user accounts in which the messageis to be shared.
 5. The messaging system of claim 4, wherein the sharelist authorizes one or more user modification privileges to be providedto at least one of the one or more identified user accounts, and whereinthe authorized one or more user modifications include modification of atleast the message or the share list.
 6. The messaging system of claim 5,wherein the user modification privileges include one or more of: editingprivileges, deletion privileges, modification of share privileges withrespect to one or more identified user accounts, or identification ofadditional user accounts in which the message is to be shared.
 7. Themessaging system of claim 4, wherein the share list specifies apredetermined time in which the message is to be deleted.
 8. Themessaging system of claim 7, further comprising a single instancestorage module configured to store the message as a single instance. 9.The messaging system of claim 8, wherein the predetermined timespecified in the share list is provided as a directive with respect to atime, time period, or an event that is to trigger deletion of themessage data from the system.
 10. The messaging system of claim 9,wherein the share module is configured to delete the message from thesingle instance storage module in accordance with the directive definedin the share list.
 11. The messaging system of claim 1, wherein theshare module comprises a notification module configured to generate anotification of the message to one or more user accounts in which themessage is to be shared.
 12. The messaging system of claim 11, whereinthe user identifying data further includes information used by themessage database server to identify one or more user communicationdevices to which the notification module is to transmit the generatednotification.
 13. The messaging system of claim 11, wherein the sharemodule comprises a retention module configured to clean the messagedatabase server of the notification and the messaging data, includingthe share list, when the message is deleted.
 14. The messaging system ofclaim 11, wherein the user identifying data comprises a first userID,and wherein, when the first userID is modified to a second userID by theuser, the first userID is modified to the second userID in all addressbooks and block lists that reference the first userID.
 15. A method ofproviding an electronic messaging service with a message databaseserver, the method comprising: maintaining, with an account module, useraccounts, each of the user accounts associated with user identifyingdata including a first password required to access the user account;receiving message data from user communication devices associated withthe user accounts, the message data including a message andidentification of one or more of the user accounts maintained by theaccount module with which the message is to be shared; sharing themessage with the one or more identified user accounts; and issuing asecond password to one of the user accounts upon request, and wherein,when the second password is used to access the user account, revertingthe user account to an original state wherein all personalizedinformation, including payment information, associated with the useraccount is deleted and unrecoverable.
 16. The method of claim 15,further comprising invalidating the second password if the firstpassword is used to access the user account before the second passwordis used to access the user account.
 17. The method of claim 16, furthercomprising invalidating the second password if the first password isused to access the user account before the second password is used toaccess the user account, and invalidating the first password if thesecond password is used to access the user account before the firstpassword.
 18. A computer readable device comprising instructions, whenloaded and executed by a processor, cause the processor to performoperations, the operations comprising: maintaining, with an accountmodule, user accounts, each of the user accounts associated with useridentifying data including a first password required to access the useraccount; receiving message data from user communication devicesassociated with the user accounts, the message data including a messageand identification of one or more of the user accounts maintained by theaccount module with which the message is to be shared; sharing themessage with the one or more identified user accounts; and issuing asecond password to one of the user accounts upon request, and wherein,when the second password is used to access the user account, revertingthe user account to an original state wherein all personalizedinformation, including payment information, associated with the useraccount is deleted and unrecoverable.
 19. The computer readable deviceof claim 18, further comprising invalidating the second password if thefirst password is used to access the user account before the secondpassword is used to access the user account.
 20. The computer readabledevice of claim 18, further comprising invalidating the second passwordif the first password is used to access the user account before thesecond password is used to access the user account, and invalidating thefirst password if the second password is used to access the user accountbefore the first password.